Method for optimal path selection for data traffic undergoing high processing or queuing delay

ABSTRACT

Described embodiments provide systems and methods for path selection proportional to a penalty delay in processing packets. A server-side intermediary may identify a delay penalty for processing packets of a server destined for a client. The server-side intermediary may be in communication via links of different latencies with a client-side intermediary. The server-side intermediary may select a second link with a latency that deviates from the lowest latency of a first link by the delay penalty. The server-side intermediary may transmit, to the client-side intermediary, duplicates of the packets via the selected second link with information indicating to hold the duplicates at the client-side intermediary. The server-side intermediary may receive an indication to drop or send the duplicates to the client. The server-side intermediary may transmit the indication to the client-side intermediary to drop or send the duplicates according to the indication.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to and thebenefit of U.S. patent application Ser. No. 16/238,865, titled “METHODFOR OPTIMAL PATH SELECTION FOR DATA TRAFFIC UNDERGOING HIGH PROCESSINGOR QUEING DELAY,” and filed on Jan. 3, 2019, the contents of all ofwhich are hereby incorporated herein by reference in its entirety forall purposes.

FIELD OF THE DISCLOSURE

The present application generally relates to routing of packets. Inparticular, the present application relates to systems and methods forpath selection proportional to a penalty delay in processing packets.

BACKGROUND

A network device may send packets to another network device via acommunication path for accessing resources for an application. Thepackets may undergo delay in arriving at the destined network device.The delay may be due to various factors, such as processing andbuffering of multiple packets at each network device along thecommunication path and traversal over the communication path itself.

BRIEF SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features, nor is it intended to limit the scope of the claimsincluded herewith.

Network devices may exchange packets with one another usingcommunication channels through a network. For example, intermediarydevices (e.g., middle box devices) deployed between clients and serversdistributed across branch offices and data centers may use site-to-sitecommunication paths to exchange the packets through a software-definedwide-area network (SD-WAN). As these packets travel toward the destinednetwork device from one intermediary device to another intermediarydevice through one of the communication paths of the network, thepackets may experience delay. There may be numerous reasons for thedelay in arrival of the packet, such as traversal over the networkitself and additional processing and buffering at each network device.One of the major contributors to the delay from additional processingand buffering of the packets may be modules that can perform heavypacket processing, such a security appliance at a data center site.Security appliances may be placed on a server-side of the network as aseparate device or in the sever-side intermediary device itself, and maymonitor packets for signatures correlating with vulnerable traffic. Suchappliances may queue and buffer packets for as long as 100 ms to inspectfor such signatures. While inspecting packets for signs of vulnerabilitymay provide additional security, the heavy processing performed by suchappliances may incur additional delay. The delay in the delivery ofpacket through the communication paths of the network may lead to awhole host of deleterious effects on communication, such as latency,jitter, and packet loss, among others.

To address the technical challenges arising from delays in the sendingof the packets through the network, the intermediary devices may selectan optimal communication path with the best path yield and betterperformance for traffic based on an estimated delay. To this end, theserver-side intermediary device on the same side (e.g., at the datacenter) as the heavy processing module (e.g., security inspectionmodule) may detect or identify a penalty delay incurred from the heavyprocessing of different types of traffic. With the identification, theserver-side intermediary device on the same side of the module mayselect the communication path through the network that is proportionalto the penalty delay. As the data traffic is processed in the module(e.g., security inspector), the server-side intermediary device mayduplicate and send the traffic to the other side (e.g., branch office)through the selected path. The client-side intermediary device in turnmay buffer the received traffic on a queue. As the traffic is buffered,the client-side intermediary device may wait until a control signal isreceived via the selected communication path. The control signal may begenerated and then transmitted by the server-side intermediary device tothe client-side intermediary device to drop or forward the packet. Inthis framework, the server-side intermediary device may handle theselection of communication path depending on the cause for the penaltydelay.

First, one cause of the penalty delay may be from buffering of packetsprior to the heavy processing of the packets at the server-sideintermediary device on the same side (e.g., the data center side) as theheavy processing module. The server-side intermediary device itself mayhave the heavy processing module (e.g., security appliance) incorporatedas part of the functionality. In such cases, inbound latency mayincrease at the server-side intermediary device, and may act as apotential bottleneck in network communications and contribute to theoverall delay in the delivery of the packets. For example, there may bea configured threshold in the communications of the network (e.g., 20ms) beyond which the packets are to be duplicated and forward to thebranch-side intermediary device.

Based on the delay penalty from additional buffering, the server-sideintermediary device may select a communication path. In selecting thecommunication path, the server-side intermediary device may check allthe available communication paths with the client-side intermediarydevice to identify a total delay in each communication path. Forexample, a first communication path may have a delay of 50 ms, a secondcommunication path may have a delay of 60 ms, and a third communicationpath may have a delay of 70 ms. Due to the configured threshold, packetswith a delay greater than the configured threshold (e.g., 20 ms) in thequeue of the security appliance may be duplicated and sent to theclient-side intermediary device. The exchange of packets may have a holdflag and may indicate an amount of delay (e.g., at least 20 ms).

With the determination of the delay in each communication path, theserver-side intermediary device may determine a deviation in the delayin each path relative to the path with the lowest delay. Continuing fromthe example above, the first communication path may be the path with thelowest delay. Relative to the first communication path, the secondcommunication path may have a deviation of 10 ms and the thirdcommunication path may have a deviation of 20 ms. The server-sideintermediary device may select the communication path with the deviationfrom the best delay that is less than or equal to the configuredthreshold and that is not also the best communication path. In thisexample, the server-side intermediary device may select the thirdcommunication path, because the deviation of the third communicationpath is equal to the configured threshold of 20 ms.

Second, another cause in the penalty delay may be from signaturematching delay in a dedicated appliance (e.g., a security appliance)that apply heavy processing to packets separate of the server-sideintermediary device. For example, a security policy may specify that thedata traffic is to be gathered and held at the security appliance for acertain number of packets (e.g., five packets) to generate a signaturefor the traffic. If the connection is in an early state, the congestionwindow size may be less than the specified number of packets (e.g., fourpackets). As such, two round trip times (RTTs) from the server to thesecurity appliance may be performed to transmit the five packets, withthe first RTT for the first four packets and the second RTT for the lastfifth packet. Ignoring transmission delays, the net time consumed totransfer the packets from the server to the security appliance in thedata center may be multiplied as a result to transmit the entire set ofpackets. In the current example, if the RTT between the server andsecurity appliance is 30 ms, the total transfer time spent may be now 60ms, as two RTTs may be spent to transfer all five packets.

Using the delay penalty due to signature matching, the server-sideintermediary device may select a communication path through the network.Similar with the other case, the server-side intermediary device maycheck all the available communication paths with the client-sideintermediary device to identify a total delay in each communicationpath. For example, a first communication path may have a delay of 50 ms,a second communication path may have a delay of 60 ms, and a thirdcommunication path may have a delay of 70 ms. With signature matching,packets with a delay greater than the RTT (e.g., 30 ms) in the queue ofthe security appliance may be duplicated and sent to the client-sideintermediary device. The exchange of packets may have a hold flag andmay indicate an amount of delay (e.g., at least 30 ms) to specify thatthe client-side intermediary device is to buffer the packet for theamount. The server-side intermediary device may select the communicationpath with the deviation from the best delay that has at most the RTT asthe delay. In this example, the server-side intermediary device mayselect the third communication path, because the third communicationpath has a delay of 20 ms greater than the delay of the firstcommunication path. Over the selected communication path, theserver-side intermediary device may proceed to send a set of packets fora signature in sequence to the client-side intermediary device. Theserver-side intermediary device may also identify the communication pathwith the least delay to send over remaining packets for the signaturereceived after the congestion window size. Using the previous example,the communication path with the least delay may be the firstcommunication path.

When remaining packets after the prior set of packets for the signaturearrives, the server-side appliance may send the packets with a controlsignal specifying whether to hold or drop the prior packets at theclient-side intermediary device over the best communication path.Ignoring transmission delays, the net latency in sending the set ofpackets for one signature may be equal to the sum of the RTT and thetotal delay in the selected communication path. From the previousexample, the net latency from sending the first four packets over thethird communication path may be equal to 100 ms for the RTT of 30 ms andthe total delay of the third communication path of 70 ms. Moreover, thenet latency in sending the remaining packets received after thecongestion window size may be equal to the sum of the RTT and the totaldelay in the best communication path. In the example, the net latencyfrom sending the last fifth packet over the first communication path maybe equal to 110 ms for the RTT of 30 ms for the first four packets, theRTT of 30 ms for the fifth packet, and the total delay of the firstcommunication path of 50 ms. Thus, the total effective time for theentire set of packets may be equal to the maximum of the net latency insending the set of packets for one signature and the net latency inssending the remaining packets received after the congestion time window.Continuing with the previous example, the total effective time may be110 ms from the net latency due to sending of the fifth packet over thefirst communication path.

In either scenario, once the communication path is selected, theserver-side intermediary device may initiate transmission of the packetsto the client-side intermediary device via the communication path to bebuffered at the client-side intermediary device until furtherinstruction. The client-side intermediary device may have a limit to thenumber of packets that may be buffered, and may transmit a feedbacksignal to the server-side intermediary device if the number is exceeded.As the heavy processing is being performed (e.g., security inspection),the server-side intermediary device may send a control signal to theclient-side intermediary device to either send or drop the bufferedpackets. The control signal may include a range of sequence numbers withthe specified instruction to send or drop the packets associated withthe sequence numbers. In this manner, this configuration of the networkdevices may prevent the communication path with the least delay frombeing loaded with too many packets. Instead, the configuration mayresult in the utilization of the optimal communication, and may reduceor eliminate latency, jitter, and packet loss in the network.

An aspect provides a method for path selection proportional to a penaltydelay in processing packets. A first device intermediary to a pluralityof a clients and one or more servers may identify a delay penalty forprocessing one or more packets of a server of the one or more serversdestined for a client of the plurality of clients. The first device maybe in communication via a plurality of links of different latencies witha second device intermediary to the one or more clients and the firstdevice. The first device may select, from the plurality of links otherthan a first link of the plurality of links with a lowest latency, asecond link with a latency that deviates from the lowest latency of thefirst link by at least the delay penalty. The first device may transmit,to the second device, duplicates of the one or more packets to thesecond device via the selected second link with information indicatingto the second device to hold the duplicates of one or more packets atthe second device. The first device may receive an indication to one ofdrop or send the duplicates of the one or more packets to the client.The first device may transmit the indication to the second device to oneof drop or send the duplicates of the one or more packets according tothe indication.

In some embodiments, the second device may transmit the duplicates ofthe one or more packets to the client instead of the one or more packetsresponsive to the indication from the first device indicating to sendthe duplicates of the one or more packets. In some embodiments, thesecond device may drop the duplicates of the one or more packets so thatthe client does not receive either the one or more packets or theduplicates of the one or more packets.

In some embodiments, the first device may receive, from a third devicethe duplicates of the one or more packets. In some embodiments, thefirst device may generate the duplicates of the one or more packets. Insome embodiments, the first device may identify the delay penalty from athird device processing the one or more packets of the server. In someembodiments, the third device may perform security inspection on the oneor more packets of the server and wherein the delay penalty correspondsto a buffering delay for processing the one or more packets at the thirddevice.

In some embodiments, the first device may identify the delay penaltycorresponding to one or more round trip times to send a number of theone or more packets between a third device and the server. In someembodiments, the third device may perform security inspection on the oneor more packets of the server and wherein the number of packets is basedat least on a number of packets for the third device to performsignature matching on the one or more packets. In some embodiments, theplurality of links may include one of a wide area network (WAN) link ora broadband link.

Another aspect provides a system for path selection proportional to apenalty delay in processing packets. The system may include a firstdevice. The first device may be intermediary to a plurality of a clientsand one or more servers. The first device may identify a delay penaltyfor processing one or more packets of a server of the one or moreservers destined for a client of the plurality of clients. The firstdevice may be in communication via a plurality of links of differentlatencies with a second device intermediary to the one or more clientsand the first device. The first device may select, from the plurality oflinks other than a first link of the plurality of links with a lowestlatency, a second link with a latency that deviates from the lowestlatency of the first link by at least the delay penalty. The firstdevice may transmit, to the second device, duplicates of the one or morepackets to the second device via the selected second link withinformation indicating to the second device to hold the duplicates ofone or more packets at the second device. The first device may receivean indication to one of drop or send the duplicates of the one or morepackets to the client. The first device may transmit the indication tothe second device to one of drop or send the duplicates of the one ormore packets according to the indication.

In some embodiments, the second device may transmit the duplicates ofthe one or more packets to the client instead of the one or more packetsresponsive to the indication from the first device indicating to sendthe duplicates of the one or more packets. In some embodiments, thesecond device may drop the duplicates of the one or more packets so thatthe client does not receive either the one or more packets or theduplicates of the one or more packets.

In some embodiments, the first device may receive, from a third device,the duplicates of the one or more packets. In some embodiments, thefirst device may generate the duplicates of the one or more packets. Insome embodiments, the first device may identify the delay penalty from athird device processing the one or more packets of the server. In someembodiments, third device may perform security inspection on the one ormore packets of the server and wherein the delay penalty corresponds toa buffering delay for processing the one or more packets at the thirddevice.

In some embodiments, the first device may identify the delay penaltycorresponding to one or more round trip times to send a number of theone or more packets between a third device and the server. In someembodiments, the third device may perform security inspection on the oneor more packets of the server and wherein the number of packets is basedat least on a number of packets for the third device to performsignature matching on the one or more packets. In some embodiments, theplurality of links may include one of a wide area network (WAN) link ora broadband link.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

Objects, aspects, features, and advantages of embodiments disclosedherein will become more fully apparent from the following detaileddescription, the appended claims, and the accompanying drawing figuresin which like reference numerals identify similar or identical elements.Reference numerals that are introduced in the specification inassociation with a drawing figure may be repeated in one or moresubsequent figures without additional description in the specificationin order to provide context for other features, and not every elementmay be labeled in every figure. The drawing figures are not necessarilyto scale, emphasis instead being placed upon illustrating embodiments,principles and concepts. The drawings are not intended to limit thescope of the claims included herewith.

FIG. 1A is a block diagram of a network computing system, in accordancewith an illustrative embodiment;

FIG. 1B is a block diagram of a network computing system for deliveringa computing environment from a server to a client via an appliance, inaccordance with an illustrative embodiment;

FIG. 1C is a block diagram of a computing device, in accordance with anillustrative embodiment;

FIG. 2 is a block diagram of an appliance for processing communicationsbetween a client and a server, in accordance with an illustrativeembodiment;

FIG. 3 is a block diagram of a virtualization environment, in accordancewith an illustrative embodiment;

FIG. 4 is a block diagram of a cluster system, in accordance with anillustrative embodiment;

FIG. 5 is a block diagram of an embodiment of a system for pathselection proportional to a penalty delay in processing packets; and

FIG. 6 is a flow diagram of an embodiment of a method for path selectionproportional to a penalty delay in processing packets.

The features and advantages of the present solution will become moreapparent from the detailed description set forth below when taken inconjunction with the drawings, in which like reference charactersidentify corresponding elements throughout. In the drawings, likereference numbers generally indicate identical, functionally similar,and/or structurally similar elements

DETAILED DESCRIPTION

For purposes of reading the description of the various embodimentsbelow, the following descriptions of the sections of the specificationand their respective contents may be helpful:

Section A describes a network environment and computing environmentwhich may be useful for practicing embodiments described herein;

Section B describes embodiments of systems and methods for delivering acomputing environment to a remote user;

Section C describes embodiments of systems and methods for virtualizingan application delivery controller;

Section D describes embodiments of systems and methods for providing aclustered appliance architecture environment; and

Section E describes embodiments of systems and methods for pathselection proportional to a penalty delay in processing packets.

A. Network and Computing Environment

Referring to FIG. 1A, an illustrative network environment 100 isdepicted. Network environment 100 may include one or more clients102(1)-102(n) (also generally referred to as local machine(s) 102 orclient(s) 102) in communication with one or more servers 106(1)-106(n)(also generally referred to as remote machine(s) 106 or server(s) 106)via one or more networks 104(1)-104 n (generally referred to asnetwork(s) 104). In some embodiments, a client 102 may communicate witha server 106 via one or more appliances 200(1)-200 n (generally referredto as appliance(s) 200 or gateway(s) 200).

Although the embodiment shown in FIG. 1A shows one or more networks 104between clients 102 and servers 106, in other embodiments, clients 102and servers 106 may be on the same network 104. The various networks 104may be the same type of network or different types of networks. Forexample, in some embodiments, network 104(1) may be a private networksuch as a local area network (LAN) or a company Intranet, while network104(2) and/or network 104(n) may be a public network, such as a widearea network (WAN) or the Internet. In other embodiments, both network104(1) and network 104(n) may be private networks. Networks 104 mayemploy one or more types of physical networks and/or network topologies,such as wired and/or wireless networks, and may employ one or morecommunication transport protocols, such as transmission control protocol(TCP), internet protocol (IP), user datagram protocol (UDP) or othersimilar protocols.

As shown in FIG. 1A, one or more appliances 200 may be located atvarious points or in various communication paths of network environment100. For example, appliance 200 may be deployed between two networks104(1) and 104(2), and appliances 200 may communicate with one anotherto work in conjunction to, for example, accelerate network trafficbetween clients 102 and servers 106. In other embodiments, the appliance200 may be located on a network 104. For example, appliance 200 may beimplemented as part of one of clients 102 and/or servers 106. In anembodiment, appliance 200 may be implemented as a network device such asCitrix networking (formerly NetScaler®) products sold by Citrix Systems,Inc. of Fort Lauderdale, Fla.

As shown in FIG. 1A, one or more servers 106 may operate as a serverfarm 38. Servers 106 of server farm 38 may be logically grouped, and mayeither be geographically co-located (e.g., on premises) orgeographically dispersed (e.g., cloud based) from clients 102 and/orother servers 106. In an embodiment, server farm 38 executes one or moreapplications on behalf of one or more of clients 102 (e.g., as anapplication server), although other uses are possible, such as a fileserver, gateway server, proxy server, or other similar server uses.Clients 102 may seek access to hosted applications on servers 106.

As shown in FIG. 1A, in some embodiments, appliances 200 may include, bereplaced by, or be in communication with, one or more additionalappliances, such as WAN optimization appliances 205(1)-205(n), referredto generally as WAN optimization appliance(s) 205. For example, WANoptimization appliance 205 may accelerate, cache, compress or otherwiseoptimize or improve performance, operation, flow control, or quality ofservice of network traffic, such as traffic to and/or from a WANconnection, such as optimizing Wide Area File Services (WAFS),accelerating Server Message Block (SMB) or Common Internet File System(CIFS). In some embodiments, appliance 205 may be a performanceenhancing proxy or a WAN optimization controller. In one embodiment,appliance 205 may be implemented as Citrix SD-WAN products sold byCitrix Systems, Inc. of Fort Lauderdale, Fla.

Referring to FIG. 1B, an example network environment 100′ for deliveringand/or operating a computing network environment on a client 102 isshown. As shown in FIG. 1B, a server 106 may include an applicationdelivery system 190 for delivering a computing environment, application,and/or data files to one or more clients 102. Client 102 may includeclient agent 120 and computing environment 15. Computing environment 15may execute or operate an application, 16, that accesses, processes oruses a data file 17. Computing environment 15, application 16 and/ordata file 17 may be delivered to the client 102 via appliance 200 and/orthe server 106.

Appliance 200 may accelerate delivery of all or a portion of computingenvironment 15 to a client 102, for example by the application deliverysystem 190. For example, appliance 200 may accelerate delivery of astreaming application and data file processable by the application froma data center to a remote user location by accelerating transport layertraffic between a client 102 and a server 106. Such acceleration may beprovided by one or more techniques, such as: 1) transport layerconnection pooling, 2) transport layer connection multiplexing, 3)transport control protocol buffering, 4) compression, 5) caching, orother techniques. Appliance 200 may also provide load balancing ofservers 106 to process requests from clients 102, act as a proxy oraccess server to provide access to the one or more servers 106, providesecurity and/or act as a firewall between a client 102 and a server 106,provide Domain Name Service (DNS) resolution, provide one or morevirtual servers or virtual internet protocol servers, and/or provide asecure virtual private network (VPN) connection from a client 102 to aserver 106, such as a secure socket layer (SSL) VPN connection and/orprovide encryption and decryption operations.

Application delivery management system 190 may deliver computingenvironment 15 to a user (e.g., client 102), remote or otherwise, basedon authentication and authorization policies applied by policy engine195. A remote user may obtain a computing environment and access toserver stored applications and data files from any network-connecteddevice (e.g., client 102). For example, appliance 200 may request anapplication and data file from server 106. In response to the request,application delivery system 190 and/or server 106 may deliver theapplication and data file to client 102, for example via an applicationstream to operate in computing environment 15 on client 102, or via aremote-display protocol or otherwise via remote-based or server-basedcomputing. In an embodiment, application delivery system 190 may beimplemented as any portion of the Citrix Workspace Suite™ by CitrixSystems, Inc., such as Citrix Virtual Apps and Desktops (formerlyXenApp® and XenDesktop®).

Policy engine 195 may control and manage the access to, and executionand delivery of, applications. For example, policy engine 195 maydetermine the one or more applications a user or client 102 may accessand/or how the application should be delivered to the user or client102, such as a server-based computing, streaming or delivering theapplication locally to the client 50 for local execution.

For example, in operation, a client 102 may request execution of anapplication (e.g., application 16′) and application delivery system 190of server 106 determines how to execute application 16′, for examplebased upon credentials received from client 102 and a user policyapplied by policy engine 195 associated with the credentials. Forexample, application delivery system 190 may enable client 102 toreceive application-output data generated by execution of theapplication on a server 106, may enable client 102 to execute theapplication locally after receiving the application from server 106, ormay stream the application via network 104 to client 102. For example,in some embodiments, the application may be a server-based or aremote-based application executed on server 106 on behalf of client 102.Server 106 may display output to client 102 using a thin-client orremote-display protocol, such as the Independent Computing Architecture(ICA) protocol by Citrix Systems, Inc. of Fort Lauderdale, Fla. Theapplication may be any application related to real-time datacommunications, such as applications for streaming graphics, streamingvideo and/or audio or other data, delivery of remote desktops orworkspaces or hosted services or applications, for exampleinfrastructure as a service (IaaS), desktop as a service (DaaS),workspace as a service (WaaS), software as a service (SaaS) or platformas a service (PaaS).

One or more of servers 106 may include a performance monitoring serviceor agent 197. In some embodiments, a dedicated one or more servers 106may be employed to perform performance monitoring. Performancemonitoring may be performed using data collection, aggregation,analysis, management and reporting, for example by software, hardware ora combination thereof. Performance monitoring may include one or moreagents for performing monitoring, measurement and data collectionactivities on clients 102 (e.g., client agent 120), servers 106 (e.g.,agent 197) or appliances 200 and/or 205 (agent not shown). In general,monitoring agents (e.g., 120 and/or 197) execute transparently (e.g., inthe background) to any application and/or user of the device. In someembodiments, monitoring agent 197 includes any of the productembodiments referred to as Citrix Analytics or Citrix ApplicationDelivery Management by Citrix Systems, Inc. of Fort Lauderdale, Fla.

The monitoring agents 120 and 197 may monitor, measure, collect, and/oranalyze data on a predetermined frequency, based upon an occurrence ofgiven event(s), or in real time during operation of network environment100. The monitoring agents may monitor resource consumption and/orperformance of hardware, software, and/or communications resources ofclients 102, networks 104, appliances 200 and/or 205, and/or servers106. For example, network connections such as a transport layerconnection, network latency, bandwidth utilization, end-user responsetimes, application usage and performance, session connections to anapplication, cache usage, memory usage, processor usage, storage usage,database transactions, client and/or server utilization, active users,duration of user activity, application crashes, errors, or hangs, thetime required to log-in to an application, a server, or the applicationdelivery system, and/or other performance conditions and metrics may bemonitored.

The monitoring agents 120 and 197 may provide application performancemanagement for application delivery system 190. For example, based uponone or more monitored performance conditions or metrics, applicationdelivery system 190 may be dynamically adjusted, for exampleperiodically or in real-time, to optimize application delivery byservers 106 to clients 102 based upon network environment performanceand conditions.

In described embodiments, clients 102, servers 106, and appliances 200and 205 may be deployed as and/or executed on any type and form ofcomputing device, such as any desktop computer, laptop computer, ormobile device capable of communication over at least one network andperforming the operations described herein. For example, clients 102,servers 106 and/or appliances 200 and 205 may each correspond to onecomputer, a plurality of computers, or a network of distributedcomputers such as computer 101 shown in FIG. 1C.

As shown in FIG. 1C, computer 101 may include one or more processors103, volatile memory 122 (e.g., RAM), non-volatile memory 128 (e.g., oneor more hard disk drives (HDDs) or other magnetic or optical storagemedia, one or more solid state drives (SSDs) such as a flash drive orother solid state storage media, one or more hybrid magnetic and solidstate drives, and/or one or more virtual storage volumes, such as acloud storage, or a combination of such physical storage volumes andvirtual storage volumes or arrays thereof), user interface (UI) 123, oneor more communications interfaces 118, and communication bus 150. Userinterface 123 may include graphical user interface (GUI) 124 (e.g., atouchscreen, a display, etc.) and one or more input/output (I/O) devices126 (e.g., a mouse, a keyboard, etc.). Non-volatile memory 128 storesoperating system 115, one or more applications 116, and data 117 suchthat, for example, computer instructions of operating system 115 and/orapplications 116 are executed by processor(s) 103 out of volatile memory122. Data may be entered using an input device of GUI 124 or receivedfrom I/O device(s) 126. Various elements of computer 101 may communicatevia communication bus 150. Computer 101 as shown in FIG. 1C is shownmerely as an example, as clients 102, servers 106 and/or appliances 200and 205 may be implemented by any computing or processing environmentand with any type of machine or set of machines that may have suitablehardware and/or software capable of operating as described herein.

Processor(s) 103 may be implemented by one or more programmableprocessors executing one or more computer programs to perform thefunctions of the system. As used herein, the term “processor” describesan electronic circuit that performs a function, an operation, or asequence of operations. The function, operation, or sequence ofoperations may be hard coded into the electronic circuit or soft codedby way of instructions held in a memory device. A “processor” mayperform the function, operation, or sequence of operations using digitalvalues or using analog signals. In some embodiments, the “processor” canbe embodied in one or more application specific integrated circuits(ASICs), microprocessors, digital signal processors, microcontrollers,field programmable gate arrays (FPGAs), programmable logic arrays(PLAs), multi-core processors, or general-purpose computers withassociated memory. The “processor” may be analog, digital ormixed-signal. In some embodiments, the “processor” may be one or morephysical processors or one or more “virtual” (e.g., remotely located or“cloud”) processors.

Communications interfaces 118 may include one or more interfaces toenable computer 101 to access a computer network such as a LAN, a WAN,or the Internet through a variety of wired and/or wireless or cellularconnections.

In described embodiments, a first computing device 101 may execute anapplication on behalf of a user of a client computing device (e.g., aclient 102), may execute a virtual machine, which provides an executionsession within which applications execute on behalf of a user or aclient computing device (e.g., a client 102), such as a hosted desktopsession, may execute a terminal services session to provide a hosteddesktop environment, or may provide access to a computing environmentincluding one or more of: one or more applications, one or more desktopapplications, and one or more desktop sessions in which one or moreapplications may execute.

Additional details of the implementation and operation of networkenvironment 100, clients 102, servers 106, and appliances 200 and 205may be as described in U.S. Pat. No. 9,538,345, issued Jan. 3, 2017 toCitrix Systems, Inc. of Fort Lauderdale, Fla., the teachings of whichare hereby incorporated herein by reference.

B. Appliance Architecture

FIG. 2 shows an example embodiment of appliance 200. As describedherein, appliance 200 may be implemented as a server, gateway, router,switch, bridge or other type of computing or network device. As shown inFIG. 2, an embodiment of appliance 200 may include a hardware layer 206and a software layer 205 divided into a user space 202 and a kernelspace 204. Hardware layer 206 provides the hardware elements upon whichprograms and services within kernel space 204 and user space 202 areexecuted and allow programs and services within kernel space 204 anduser space 202 to communicate data both internally and externally withrespect to appliance 200. As shown in FIG. 2, hardware layer 206 mayinclude one or more processing units 262 for executing software programsand services, memory 264 for storing software and data, network ports266 for transmitting and receiving data over a network, and encryptionprocessor 260 for encrypting and decrypting data such as in relation toSecure Socket Layer (SSL) or Transport Layer Security (TLS) processingof data transmitted and received over the network.

An operating system of appliance 200 allocates, manages, or otherwisesegregates the available system memory into kernel space 204 and userspace 202. Kernel space 204 is reserved for running kernel 230,including any device drivers, kernel extensions or other kernel relatedsoftware. As known to those skilled in the art, kernel 230 is the coreof the operating system, and provides access, control, and management ofresources and hardware-related elements of application. Kernel space 204may also include a number of network services or processes working inconjunction with cache manager 232.

Appliance 200 may include one or more network stacks 267, such as aTCP/IP based stack, for communicating with client(s) 102, server(s) 106,network(s) 104, and/or other appliances 200 or 205. For example,appliance 200 may establish and/or terminate one or more transport layerconnections between clients 102 and servers 106. Each network stack 267may include a buffer for queuing one or more network packets fortransmission by appliance 200.

Kernel space 204 may include cache manager 232, packet engine 240,encryption engine 234, policy engine 236 and compression engine 238. Inother words, one or more of processes 232, 240, 234, 236 and 238 run inthe core address space of the operating system of appliance 200, whichmay reduce the number of data transactions to and from the memory and/orcontext switches between kernel mode and user mode, for example sincedata obtained in kernel mode may not need to be passed or copied to auser process, thread or user level data structure.

Cache manager 232 may duplicate original data stored elsewhere or datapreviously computed, generated or transmitted to reduce the access timeof the data. In some embodiments, the cache manager 232 may be a dataobject in memory 264 of appliance 200, or may be a physical memoryhaving a faster access time than memory 264.

Policy engine 236 may include a statistical engine or otherconfiguration mechanism to allow a user to identify, specify, define orconfigure a caching policy and access, control and management ofobjects, data or content being cached by appliance 200, and define orconfigure security, network traffic, network access, compression orother functions performed by appliance 200.

Encryption engine 234 may process any security related protocol, such asSSL or TLS. For example, encryption engine 234 may encrypt and decryptnetwork packets, or any portion thereof, communicated via appliance 200,may setup or establish SSL, TLS or other secure connections, for examplebetween client 102, server 106, and/or other appliances 200 or 205. Insome embodiments, encryption engine 234 may use a tunneling protocol toprovide a VPN between a client 102 and a server 106. In someembodiments, encryption engine 234 is in communication with encryptionprocessor 260. Compression engine 238 compresses network packetsbi-directionally between clients 102 and servers 106 and/or between oneor more appliances 200.

Packet engine 240 may manage kernel-level processing of packets receivedand transmitted by appliance 200 via network stacks 267 to send andreceive network packets via network ports 266. Packet engine 240 mayoperate in conjunction with encryption engine 234, cache manager 232,policy engine 236 and compression engine 238, for example to performencryption/decryption, traffic management such as request-level contentswitching and request-level cache redirection, and compression anddecompression of data.

User space 202 is a memory area or portion of the operating system usedby user mode applications or programs otherwise running in user mode. Auser mode application may not access kernel space 204 directly and usesservice calls in order to access kernel services. User space 202 mayinclude graphical user interface (GUI) 210, a command line interface(CLI) 212, shell services 214, health monitor 216, and daemon services218. GUI 210 and CLI 212 enable a system administrator or other user tointeract with and control the operation of appliance 200, such as viathe operating system of appliance 200. Shell services 214 includeprograms, services, tasks, processes or executable instructions tosupport interaction with appliance 200 by a user via the GUI 210 and/orCLI 212.

Health monitor 216 monitors, checks, reports and ensures that networksystems are functioning properly and that users are receiving requestedcontent over a network, for example by monitoring activity of appliance200. In some embodiments, health monitor 216 intercepts and inspects anynetwork traffic passed via appliance 200. For example, health monitor216 may interface with one or more of encryption engine 234, cachemanager 232, policy engine 236, compression engine 238, packet engine240, daemon services 218, and shell services 214 to determine a state,status, operating condition, or health of any portion of the appliance200. Further, health monitor 216 may determine whether a program,process, service or task is active and currently running, check status,error or history logs provided by any program, process, service or taskto determine any condition, status or error with any portion ofappliance 200. Additionally, health monitor 216 may measure and monitorthe performance of any application, program, process, service, task orthread executing on appliance 200.

Daemon services 218 are programs that run continuously or in thebackground and handle periodic service requests received by appliance200. In some embodiments, a daemon service may forward the requests toother programs or processes, such as another daemon service 218 asappropriate.

As described herein, appliance 200 may relieve servers 106 of much ofthe processing load caused by repeatedly opening and closing transportlayers connections to clients 102 by opening one or more transport layerconnections with each server 106 and maintaining these connections toallow repeated data accesses by clients via the Internet (e.g.,“connection pooling”). To perform connection pooling, appliance 200 maytranslate or multiplex communications by modifying sequence numbers andacknowledgment numbers at the transport layer protocol level (e.g.,“connection multiplexing”). Appliance 200 may also provide switching orload balancing for communications between the client 102 and server 106.

As described herein, each client 102 may include client agent 120 forestablishing and exchanging communications with appliance 200 and/orserver 106 via a network 104. Client 102 may have installed and/orexecute one or more applications that are in communication with network104. Client agent 120 may intercept network communications from anetwork stack used by the one or more applications. For example, clientagent 120 may intercept a network communication at any point in anetwork stack and redirect the network communication to a destinationdesired, managed or controlled by client agent 120, for example tointercept and redirect a transport layer connection to an IP address andport controlled or managed by client agent 120. Thus, client agent 120may transparently intercept any protocol layer below the transportlayer, such as the network layer, and any protocol layer above thetransport layer, such as the session, presentation or applicationlayers. Client agent 120 can interface with the transport layer tosecure, optimize, accelerate, route or load-balance any communicationsprovided via any protocol carried by the transport layer.

In some embodiments, client agent 120 is implemented as an IndependentComputing Architecture (ICA) client developed by Citrix Systems, Inc. ofFort Lauderdale, Fla. Client agent 120 may perform acceleration,streaming, monitoring, and/or other operations. For example, clientagent 120 may accelerate streaming an application from a server 106 to aclient 102. Client agent 120 may also perform end-pointdetection/scanning and collect end-point information about client 102for appliance 200 and/or server 106. Appliance 200 and/or server 106 mayuse the collected information to determine and provide access,authentication and authorization control of the client's connection tonetwork 104. For example, client agent 120 may identify and determineone or more client-side attributes, such as: the operating system and/ora version of an operating system, a service pack of the operatingsystem, a running service, a running process, a file, presence orversions of various applications of the client, such as antivirus,firewall, security, and/or other software.

Additional details of the implementation and operation of appliance 200may be as described in U.S. Pat. No. 9,538,345, issued Jan. 3, 2017 toCitrix Systems, Inc. of Fort Lauderdale, Fla., the teachings of whichare hereby incorporated herein by reference.

C. Systems and Methods for Providing Virtualized Application DeliveryController

Referring now to FIG. 3, a block diagram of a virtualized environment300 is shown. As shown, a computing device 302 in virtualizedenvironment 300 includes a virtualization layer 303, a hypervisor layer304, and a hardware layer 307. Hypervisor layer 304 includes one or morehypervisors (or virtualization managers) 301 that allocates and managesaccess to a number of physical resources in hardware layer 307 (e.g.,physical processor(s) 321 and physical disk(s) 328) by at least onevirtual machine (VM) (e.g., one of VMs 306) executing in virtualizationlayer 303. Each VM 306 may include allocated virtual resources such asvirtual processors 332 and/or virtual disks 342, as well as virtualresources such as virtual memory and virtual network interfaces. In someembodiments, at least one of VMs 306 may include a control operatingsystem (e.g., 305) in communication with hypervisor 301 and used toexecute applications for managing and configuring other VMs (e.g., guestoperating systems 310) on device 302.

In general, hypervisor(s) 301 may provide virtual resources to anoperating system of VMs 306 in any manner that simulates the operatingsystem having access to a physical device. Thus, hypervisor(s) 301 maybe used to emulate virtual hardware, partition physical hardware,virtualize physical hardware, and execute virtual machines that provideaccess to computing environments. In an illustrative embodiment,hypervisor(s) 301 may be implemented as a Citrix Hypervisor by CitrixSystems, Inc. of Fort Lauderdale, Fla. In an illustrative embodiment,device 302 executing a hypervisor that creates a virtual machineplatform on which guest operating systems may execute is referred to asa host server.

Hypervisor 301 may create one or more VMs 306 in which an operatingsystem (e.g., control operating system 305 and/or guest operating system310) executes. For example, the hypervisor 301 loads a virtual machineimage to create VMs 306 to execute an operating system. Hypervisor 301may present VMs 306 with an abstraction of hardware layer 307, and/ormay control how physical capabilities of hardware layer 307 arepresented to VMs 306. For example, hypervisor(s) 301 may manage a poolof resources distributed across multiple physical computing devices.

In some embodiments, one of VMs 306 (e.g., the VM executing controloperating system 305) may manage and configure other of VMs 306, forexample by managing the execution and/or termination of a VM and/ormanaging allocation of virtual resources to a VM. In variousembodiments, VMs may communicate with hypervisor(s) 301 and/or other VMsvia, for example, one or more Application Programming Interfaces (APIs),shared memory, and/or other techniques.

In general, VMs 306 may provide a user of device 302 with access toresources within virtualized computing environment 300, for example, oneor more programs, applications, documents, files, desktop and/orcomputing environments, or other resources. In some embodiments, VMs 306may be implemented as fully virtualized VMs that are not aware that theyare virtual machines (e.g., a Hardware Virtual Machine or HVM). In otherembodiments, the VM may be aware that it is a virtual machine, and/orthe VM may be implemented as a paravirtualized (PV) VM.

Although shown in FIG. 3 as including a single virtualized device 302,virtualized environment 300 may include a plurality of networked devicesin a system in which at least one physical host executes a virtualmachine. A device on which a VM executes may be referred to as aphysical host and/or a host machine. For example, appliance 200 may beadditionally or alternatively implemented in a virtualized environment300 on any computing device, such as a client 102, server 106 orappliance 200. Virtual appliances may provide functionality foravailability, performance, health monitoring, caching and compression,connection multiplexing and pooling and/or security processing (e.g.,firewall, VPN, encryption/decryption, etc.), similarly as described inregard to appliance 200.

Additional details of the implementation and operation of virtualizedcomputing environment 300 may be as described in U.S. Pat. No.9,538,345, issued Jan. 3, 2017 to Citrix Systems, Inc. of FortLauderdale, Fla., the teachings of which are hereby incorporated hereinby reference.

In some embodiments, a server may execute multiple virtual machines 306,for example on various cores of a multi-core processing system and/orvarious processors of a multiple processor device. For example, althoughgenerally shown herein as “processors” (e.g., in FIGS. 1C, 2 and 3), oneor more of the processors may be implemented as either single- ormulti-core processors to provide a multi-threaded, parallel architectureand/or multi-core architecture. Each processor and/or core may have oruse memory that is allocated or assigned for private or local use thatis only accessible by that processor/core, and/or may have or use memorythat is public or shared and accessible by multiple processors/cores.Such architectures may allow work, task, load or network trafficdistribution across one or more processors and/or one or more cores(e.g., by functional parallelism, data parallelism, flow-based dataparallelism, etc.).

Further, instead of (or in addition to) the functionality of the coresbeing implemented in the form of a physical processor/core, suchfunctionality may be implemented in a virtualized environment (e.g.,300) on a client 102, server 106 or appliance 200, such that thefunctionality may be implemented across multiple devices, such as acluster of computing devices, a server farm or network of computingdevices, etc. The various processors/cores may interface or communicatewith each other using a variety of interface techniques, such as core tocore messaging, shared memory, kernel APIs, etc.

In embodiments employing multiple processors and/or multiple processorcores, described embodiments may distribute data packets among cores orprocessors, for example to balance the flows across the cores. Forexample, packet distribution may be based upon determinations offunctions performed by each core, source and destination addresses,and/or whether: a load on the associated core is above a predeterminedthreshold; the load on the associated core is below a predeterminedthreshold; the load on the associated core is less than the load on theother cores; or any other metric that can be used to determine where toforward data packets based in part on the amount of load on a processor.

For example, data packets may be distributed among cores or processesusing receive-side scaling (RSS) in order to process packets usingmultiple processors/cores in a network. RSS generally allows packetprocessing to be balanced across multiple processors/cores whilemaintaining in-order delivery of the packets. In some embodiments, RSSmay use a hashing scheme to determine a core or processor for processinga packet.

The RSS may generate hashes from any type and form of input, such as asequence of values. This sequence of values can include any portion ofthe network packet, such as any header, field or payload of networkpacket, and include any tuples of information associated with a networkpacket or data flow, such as addresses and ports. The hash result or anyportion thereof may be used to identify a processor, core, engine, etc.,for distributing a network packet, for example via a hash table,indirection table, or other mapping technique.

Additional details of the implementation and operation of amulti-processor and/or multi-core system may be as described in U.S.Pat. No. 9,538,345, issued Jan. 3, 2017 to Citrix Systems, Inc. of FortLauderdale, Fla., the teachings of which are hereby incorporated hereinby reference.

D. Systems and Methods for Providing a Distributed Cluster Architecture

Although shown in FIGS. 1A and 1B as being single appliances, appliances200 may be implemented as one or more distributed or clusteredappliances. Individual computing devices or appliances may be referredto as nodes of the cluster. A centralized management system may performload balancing, distribution, configuration, or other tasks to allow thenodes to operate in conjunction as a single computing system. Such acluster may be viewed as a single virtual appliance or computing device.FIG. 4 shows a block diagram of an illustrative computing device clusteror appliance cluster 400. A plurality of appliances 200 or othercomputing devices (e.g., nodes) may be joined into a single cluster 400.Cluster 400 may operate as an application server, network storageserver, backup service, or any other type of computing device to performmany of the functions of appliances 200 and/or 205.

In some embodiments, each appliance 200 of cluster 400 may beimplemented as a multi-processor and/or multi-core appliance, asdescribed herein. Such embodiments may employ a two-tier distributionsystem, with one appliance if the cluster distributing packets to nodesof the cluster, and each node distributing packets for processing toprocessors/cores of the node. In many embodiments, one or more ofappliances 200 of cluster 400 may be physically grouped orgeographically proximate to one another, such as a group of bladeservers or rack mount devices in a given chassis, rack, and/or datacenter. In some embodiments, one or more of appliances 200 of cluster400 may be geographically distributed, with appliances 200 notphysically or geographically co-located. In such embodiments,geographically remote appliances may be joined by a dedicated networkconnection and/or VPN. In geographically distributed embodiments, loadbalancing may also account for communications latency betweengeographically remote appliances.

In some embodiments, cluster 400 may be considered a virtual appliance,grouped via common configuration, management, and purpose, rather thanas a physical group. For example, an appliance cluster may comprise aplurality of virtual machines or processes executed by one or moreservers.

As shown in FIG. 4, appliance cluster 400 may be coupled to aclient-side network 104 via client data plane 402, for example totransfer data between clients 102 and appliance cluster 400. Client dataplane 402 may be implemented a switch, hub, router, or other similarnetwork device internal or external to cluster 400 to distribute trafficacross the nodes of cluster 400. For example, traffic distribution maybe performed based on equal-cost multi-path (ECMP) routing with nexthops configured with appliances or nodes of the cluster, open-shortestpath first (OSPF), stateless hash-based traffic distribution, linkaggregation (LAG) protocols, or any other type and form of flowdistribution, load balancing, and routing.

Appliance cluster 400 may be coupled to a second network 104′ via serverdata plane 404. Similar to client data plane 402, server data plane 404may be implemented as a switch, hub, router, or other network devicethat may be internal or external to cluster 400. In some embodiments,client data plane 402 and server data plane 404 may be merged orcombined into a single device.

In some embodiments, each appliance 200 of cluster 400 may be connectedvia an internal communication network or backplane 406. Backplane 406may enable inter-node or inter-appliance control and configurationmessages, for inter-node forwarding of traffic, and/or for communicatingconfiguration and control traffic from an administrator or user tocluster 400. In some embodiments, backplane 406 may be a physicalnetwork, a VPN or tunnel, or a combination thereof.

Additional details of cluster 400 may be as described in U.S. Pat. No.9,538,345, issued Jan. 3, 2017 to Citrix Systems, Inc. of FortLauderdale, Fla., the teachings of which are hereby incorporated hereinby reference.

E. Systems and Methods for Path Selection Proportional to a PenaltyDelay in Processing Packets

Referring now to FIG. 5, depicted is a system 500 for path selectionproportional to a penalty delay in processing packets. In overview, thesystem 500 may include one or more clients 102 a-n (hereinaftergenerally referred to as clients 102), one or more servers 106 a-n(hereinafter generally referred to as servers 106), and one or moreappliances 200 a-n (e.g., intermediary devices, network devices, middlebox devices, proxy devices). The one or more appliances 200 a-n may bedeployed between the clients 102 and the servers 106. The one or moreappliances 200 a-n may include at least one client-side appliance 200 a,at least one server-side appliance 200 b, and at least one dedicatedappliance 200 c. In some embodiments, the functionalities of thesecurity appliances 200 c may be incorporated or be part of theserver-side appliance 200 b.

The clients 102, the servers 106, and the appliances 200 a-n may becommunicatively connected to one another through one or more networks104, 104′, and 104″. The one or more clients 102 and at least one aclient-side appliance 200 a may be in communication with one another viaat least one client-side network 104. In some embodiments, the clients102 may reside in at least one branch office and the client-side network104 may be a private network (e.g., a local area network (LAN) or widearea network (WAN)) between the clients 102 and the client-sideappliances 200 a. One or more appliances 200 a-n (e.g., the client-sideappliance 200 a, a server-side appliance 200 b, and a dedicatedappliance 200 c) may be in communication with one another via at leastone intermediary network 104′. In some embodiments, the intermediarynetwork 104′ may be a private network (e.g., a LAN, WAN, or asoftware-defined wide area network (SD-WAN)) among two or more of theappliances 200 a-n (e.g., the client-side appliance 200 a, theserver-side appliance 200 b, and the dedicated appliance 200 c). The oneor more servers 106 and at least one appliance 200 a-n (e.g., theserver-side appliance 200 b and the dedicated appliance 200 c) may be incommunication with one another via at least one server-side network104″. In some embodiments, the servers 106 may reside in at least onedata center, and the server-side network 104″ may be a private network(e.g., a local area network (LAN) or wide area network (WAN)) or apublic network (e.g., the Internet) among the server-side appliances 200b, the dedicated appliance 200 c, and the servers 106.

The client-side appliance 200 a may include at least one communicationengine 505 a, at least one delay estimator 510 a, at least one pathquality estimator 515 a, at least one link selector 520 a, at least onedelivery handler 525 a, at least one database 530 a, among others. Theserver-side appliance 200 b may include at least one communicationengine 505 b, at least one delay estimator 510 b, at least one pathquality estimator 515 b, at least one link selector 520 b, at least onedelivery handler 525 b, and at least one database 530 b. The client-sideappliance 200 a and the server-side appliance 200 b may be connected viaone or more links 535 a-n (sometimes herein referred to as communicationpaths) established over the network 104′. The dedicated appliance 200 c(sometimes herein referred to as a security appliance) may include atleast one packet processor 540 (sometimes herein referred to as asecurity inspector or packet inspector) and at least one database 530 c.In some embodiments, the server-side appliance 500 b may also includethe at least one packet processor 540 of the dedicated appliance 200 c.An appliance 200 a-n can include or correspond to any type or form ofintermediary device, network device, middle box device and/or proxydevice, and so on.

The systems and methods of the present solution may be implemented inany type and form of device, including clients, servers and/orappliances 200. As referenced herein, a “server” may sometimes refer toany device in a client-server relationship, e.g., an appliance 200 a ina handshake with a client device 102. The present systems and methodsmay be implemented in any intermediary device or gateway, such as anyembodiments of the appliance or devices 200 a-n described herein. Someportion of the present systems and methods may be implemented as part ofa packet processing engine and/or virtual server of an appliance, forinstance. The systems and methods may be implemented in any type andform of environment, including multi-core appliances, virtualizedenvironments and/or clustered environments described herein.

In further detail, the client-side appliance 200 a and the server-sideappliance 200 b may be in communication with each other. Thecommunication engine 505 a of the client-side appliance 200 a or thecommunication engine 505 b of the server-side appliance 200 b mayinitiate, set up, or establish a set of links 535 a-n through thenetwork 104′. The links 535 a-n established over the network 104′ mayinclude one or more WAN links, one or more LAN links, or one or morebroadband links, among others. In some embodiments, each communicationpath 530 a-n may be established in accordance with any number of networkprotocols for point-to-point communications, such as the Generic RoutingEncapsulation (GRE), virtual private network (VPN), Secure Sockets Layervirtual private network (SSLVPN), and Internet Protocol Security(IPSec), among others. The links 535 a-n may have various networkperformances, in terms of bandwidth, latency, throughput, error rate,jitter, and number of hops between the client-side appliance 200 a andthe server-side appliance 200 b, among other measures. In someembodiments, the links 535 a-n may have different latencies. Thelatencies may correspond to an amount of time that one packet consumesto travel from the client-side appliance 200 a to the server-sideappliance 200 b or from the server-side appliance 200 b to theclient-side appliance 200 a. The network performances may affect thelatencies of the links 535 a-n.

With the establishment of the links 535 a-n, the communication engine505 a and the communication engine 505 b can exchange one or morepackets between the client-side appliance 200 a and the server-sideappliance 200 b. The communication engine 505 a on the client-sideappliance 200 a may receive one or more packets from one of the clients102 via the network 104. The packets from the client 102 may be destinedto at least one of the servers 106. For example, the packets from theclient 102 may have a destination address referencing or correspondingto one of the servers 106. Upon receipt of the packets from the client102, the communication engine 505 a may forward and send the packets viaat least one of the links 535 a-n to the server-side appliance 200 b viathe network 104′. Subsequently, the communication engine 505 b of theserver-side appliance 200 b may receive the packets from the client-sideappliance 200 a via at least one of the links 535 a-n via the network104′. The communication engine 505 b may then forward and send thepackets to the destined one or more servers 106 via the network 104″.

Conversely, the communication engine 505 b on the server-side appliance200 b may receive one or more packets from one of the servers 106 viathe network 104″. The packets from the server 106 may be destined to atleast one of the clients 102. For example, the packets from the server106 may have a destination address referencing or corresponding to oneof the clients 102. Upon receipt of the packets from the server 106, thecommunication engine 505 b may forward and send the packets via at leastone of the links 535 a-n to the client-side appliance 200 a via thenetwork 104′. Subsequently, the communication engine 505 a of theclient-side appliance 200 a may receive the packets from the server-sideappliance 200 b via at least one of the links 535 a-n via the network104′. The communication engine 505 a may then forward and send thepackets to the destined client 102 via the network 104.

Prior to the transmission of packets to the client-side appliance 200 avia the network 104′, the server-side appliance 200 b or the dedicatedappliance 200 c may perform additional processing on the packets. Insome embodiments, the packet processor 540 may perform additionalprocessing on the packets, such as encryption (e.g., cryptographichash), tokenization, and formatting, among others. In some embodiments,the packet processor 540 may perform security inspection on at least oneof the packets received from the servers 106. As described above, thefunctionalities of the packet processor 540 may be incorporated on theserver-side appliance 200 b or may be performed on a separate dedicatedappliance 200 c. The security inspection of packets may, for example,include: security information and event management (SIEM), intrusiondetection, packet inspection, intrusion prevention, data exfiltrationdetection, data exfiltration prevention, firewall, repeat attackprevention, and repeat attack detection, among others. The performanceof the security inspection (or other processing on the packets) may be acomputationally complex and consume a large amount of processorresources and memory, and may add to the delay in the packets inreaching at the client 102. In some embodiments, concurrent toperforming the processing on the packets, the packet processor 540executing on the dedicated appliance 200 c may generate duplicates ofthe packets from the server 106. Each time a packet is duplicated, thepacket processor 540 may parse the packet to identify a sequence numberof the packet. The packet processor 540 may record or maintain thesequence numbers of the duplicated packets. The packet processor 540 maysend the duplicates of the packets to the server-side appliance 200 b.

In performing the security inspection or additional processing to thepackets, the packet processor 540 may buffer or store packets receivedfrom the server 106. The packets may be maintained on a storage (e.g.,on the database 530 b of the server-side appliance 200 b or the database530 c of the dedicated appliance 200 c). In some embodiments, the packetprocessor 540 may maintain a counter to keep track of a number ofbuffered packets. The packet processor 540 may compare the number of thebuffer to a threshold number. The threshold number may correspond to aminimum number of packets prior to performance of processing of the setof buffered packets. In some embodiments, the packet processor 540 maymaintain a timer to keep track of a time elapsed since receipt of afirst packet of the stored packets. The security engine 535 may comparethe elapsed time to a threshold time limit. The threshold time limit maycorrespond to a maximum wait time prior to performance of processing ofthe set of stored packets. Once the number of packet reaches thethreshold number or the elapsed time reaches the threshold time limit,the packet processor 540 may forward the packets to the clients 102 viato the network 104′. The performance of the buffering of the packets bythe packet processor 540 may add to the delay in the arrival of thepacket to the client 102.

In some embodiments, when the number of packet reaches the thresholdnumber or the elapsed time reaches the threshold time limit, the packetprocessor 540 may also perform security inspection, such as signaturematching. The packet processor 540 may generate or identify a signatureusing a set of packets received from the server 106. The signature(sometimes referred herein as an intrusion detection signature) mayinclude or correspond to a pattern of data among the set of packets,such header values and payload data. The number of packets used togenerate or identify the signature may range anywhere between 1 to10,000. But the number of received packets may be less than thethreshold number, as the elapsed time may reach the threshold time limitdue to the congestion window size of the packets. The remaining packetsmay be received subsequent to the signature comparison. The packetprocessor 540 may compare the signature identified from the set ofreceived packets with a set of prohibited signatures or with a set ofpermitted signatures. If the signature matches one of the permittedsignatures or does not match any of the prohibited signatures, thepacket processor 540 may allow the set of packets to be transmitted overthe network 104′. Conversely, if the signature matches one of theprohibited signatures or does not match any of the permitted signatures,the packet processor 540 may perform countermeasures. Thecountermeasures may include restricting the transmission of packets overthe network 104′. In some embodiments, when the number of packet reachesthe threshold number or the elapsed time reaches the threshold timelimit, the packet processor 540 may also perform other processing, suchas encryption, tokenization, and formatting. The performance of theidentification and the comparison of the signatures by the packetprocessor 540 may also add to the delay in the arrival of the packet tothe client 102.

The delay estimator 510 b executing on the server-side appliance 200 bmay identify a delay penalty for processing one or more packets from oneof the servers 106. The delay penalty may be or correspond to an amountof time to be incurred in processing the one or more packets by theserver-side appliance 200 b or the dedicated appliance 200 c. In someembodiments, the delay estimator 510 b may identify the delay penaltyfrom processing of the packets by the server-side appliance 200 b or thededicated appliance 200 c, or both. In identifying the delay penalty,the delay estimator 510 b may estimate, calculate, or otherwisedetermine the amount of time to be incurred by the one or more packetsfrom the processing. To determine the amount of time to be incurred, thedelay estimator 510 b may identify one or more operations to beperformed by the server-side appliance 200 b or the dedicated appliance200 c. The one or more operations may, for example, include: thebuffering of packets by the server-side appliance 200 b or the dedicatedappliance 200 c or the security inspection performed by the packetprocessor 540 on the server-side appliance 200 b or the dedicatedappliance 200 c. In some embodiments, the delay estimator 510 b mayidentify the delay penalty as from buffering of the packets by theserver-side appliance 200 b or the dedicated appliance 200 c. Thebuffering of packets may incur delay from the storage of the packetsprior to processing and forwarding of the packets. In some embodiments,the delay estimator 510 b may identify the delay penalty as from thesignature matching by the server-side appliance 200 b or the dedicatedappliance 200 c. The signature matching may incur delay from the time oftravel between the server-side appliance 200 b and the dedicatedappliance 200 c, the computations for comparing signatures from packets,and the subsequent forwarding of the packets.

With the identification of the one or more operations to be performed onthe packets, the delay estimator 510 b may identify or determine theamount of time incurred by the one or more packets in processing. Insome embodiments, the delay estimator 510 b may access a list specifyingthe amount of time for each operation to identify the amount of time tobe incurred in performing the operations. The list may also specify thethreshold time limit prior to processing for the operation. For example,the list may specify the threshold time limit for buffering by theserver-side appliance 200 b or the dedicated appliance 200 c prior toforwarding the packets. In some embodiments, the delay estimator 510 bmay calculate the amount of time to be incurred based on number of otherfactors. The factors may include a size of the packets, a number ofpackets, a round-trip time (RTT), and computing resources, among others.In some embodiments, the delay estimator 510 b may identify the size ofthe one or more packets from the server 106. In some embodiments, thedelay estimator 510 b may identify the number of the one or more storedpackets (e.g., on the database 530 b or 530 c). In some embodiments, thedelay estimator 510 b may determine or identify the round-trip time ofone or more packets between the server-side appliance 200 b and thededicated appliance 200 c. The delay estimator 510 b may send a testpacket to the dedicated appliance 200 c and wait for a response packetto measure the round-trip time between the server-side appliance 200 band the dedicated appliance 200 c. In some embodiments, the delayestimator 510 b may identify a consumption of computing resources on theserver-side appliance 200 b or the dedicated appliance 200 c, suchprocessor utilization and memory usage. Using these factors, the delayestimator 510 b may determine the amount of time to be incurred. In someembodiments, the delay estimator 510 b may modify adjust the amount oftime identified from the list using the factors. The delay estimator 510b may use the identified amount of time to be incurred in processing thepackets by the server-side appliance 200 b or the dedicated appliance200 c as the delay penalty.

The path quality estimator 515 b executing on the server-side appliance200 b may identify or determine a latency for each link 535 a-n. Thelatency may correspond to an amount of time that one or more packet taketo travel from the server-side appliance 200 b to the client-sideappliance 200 a. In some embodiments, the path quality estimator 515 bmay estimate, calculate, or otherwise determine the latency for eachlink 535 a-n by performing a ping test through the link 535 a-n. Inperforming the ping test, the path quality estimator 515 b may generatean echo packet for each link 535 a-n. The path quality estimator 515 bmay send the echo packet through the link 535 a-n over the network 104′to the client-side appliance 200 a. The path quality estimator 515 b maywait for a response packet from the client-side appliance 200 a via thelink 535 a-n over the network 104′. The path quality estimator 515 b maymaintain a timer to keep track of a time elapsed from transmission ofthe echo packet. Upon receipt of the response packet from theclient-side appliance 200 a, the path quality estimator 515 b mayidentify the elapsed time as the latency. The elapsed time maycorrespond to a return time trip for the link 535 a-n. In someembodiments, the path quality estimator 515 b may sort or rank the links535 a-n by the corresponding latencies.

Using the identified delay penalty and the latency of each link 535 a-n,the link selector 520 b executing on the server-side appliance 200 b mayselect at least one of the links 535 a-n. From the set of links 530 a-nover the network 104′, the link selector 520 b may select a link 535 a-nwith a latency that deviates from the lowest latency by at least thedelay penalty. In some embodiments, the link selector 520 b may selectthe single existing link 535 a-n. As opposed to multiple, there may be asingle link 535 a-n established over the network 104′ between theclient-side appliance 200 a and the server-side appliance 200 b. Inselecting the link 535 a-n, the link selector 520 b may identify thelink 535 a-n with the lowest latency. For example, a first link 535 amay have a latency of 50 ms, a second link 535 b may have a latency of60 ms, and a third link 535 c may have a latency of 70 ms. In thisexample, the link selector 520 b may identify the first link 535 a ashaving the lowest latency with 50 ms. The link selector 520 b maycompare the latencies of the remaining links 535 a-n with the lowestlatency of the corresponding link 535 a-n. In some embodiments, the linkselector 520 b may calculate or determine a deviation between thelatency of each remaining link 535 a-n and the lowest latency. Using theprevious example, the link selector 520 b may determine a deviation of10 ms for the second link 535 b (60 ms-50 ms) and a deviation of 20 msfor the third link 535 c (70 ms-50 ms).

With the determination of the deviations in the latencies, the linkselector 520 b may identify links 535 a-n with a latency deviationgreater than or equal to the delay penalty. The link selector 520 b mayalso identify links 535 a-n with a latency deviation less than the delaypenalty. The latency deviation may be the difference between the latencyof the link 535 a-n relative to the lowest latency over the links 535a-n. As explained above, the delay penalty may be or correspond to anamount of time to be incurred in processing the one or more packets bythe server-side appliance 200 b or the dedicated appliance 200 c. Thedelay penalty may, for example, correspond to an amount of time incurredfrom the buffering of the packets or from signature matching on thepackets. Continuing with the previous example, the delay penalty may befrom the amount of time incurred from the buffering of the packets, andmay be the threshold time limit of 20 ms. In this case, the linkselector 520 b may identify the second link 535 b having a latencydeviation less than the delay penalty (10 ms<20 ms) and identify thethird link 535 c having a latency deviation equal to the delay penalty(20 ms=20 ms). From the links 535 a-n identified as having a latencydeviation greater than or equal to the delay penalty, the link selector520 b may select the link 535 a-n with the lowest latency deviation. Inthe previous example, the link selector 520 b may select the third link535 c, as the third link 535 c has the latency deviation equal to thedelay penalty (20 ms) while the second link 535 b has the latencydeviation lower than the delay penalty.

In some embodiments, the link selector 520 b may identify the link 535a-n from the links 535 a-n identified as having a latency deviationclosest in value to the delay penalty. The link selector 520 b maydetermine that there are no links 535 a-n with a latency deviationgreater than or equal to the delay penalty. In response to thedetermination, the link selector 520 b may compare the latencydeviations of the remaining links 535 a-n with the delay penalty. Insome embodiments, the link selector 520 b may calculate or determine adifference between the latency deviation of the link 535 a-n and thedelay penalty. Based on the differences between the latency deviationsof the links 535 a-n and the delay penalty, the link selector 520 b mayselect one of the links 535 a-n with latency deviations less than thedelay penalty. With the determination of the differences, the linkselector 520 b may identify the link 535 a-n with the lowest differencebetween the corresponding latency deviation and the delay penalty.Continuing with the previous example, the delay penalty may be from theamount of time incurred from the signature matching, and may be theround-trip time of 30 ms. In this example, the link selector 520 b mayidentify the second link 535 b having a latency deviation less than thedelay penalty (10 ms<30 ms) and identify the third link 535 c having alatency difference also less than the penalty (20 ms<30 ms). With bothlatency deviations less than the delay penalty, the link selector 520 bmay calculate the difference between the latency deviation and the delaypenalty for the second link 535 b as 20 ms and the third link 535 c as10 ms. Based on the differences, the link selector 520 b may select thethird link 535 c for having the lowest difference between the latencydeviation and the delay penalty. In effect, the link selector 520 b maychoose the non-best link 535 a-n with the least difference from thedelay penalty.

Using the selection of at least one of the links 535 a-n, the deliveryhandler 525 b executing on the server-side appliance 200 b may transmitduplicates of the one or more packets from the server 106 to theclient-side appliance 200 a via the selected link 535 a-n. In someembodiments, the delivery handler 525 b may generate the duplicates ofthe packets from the server 106. In some embodiments, the deliveryhandler 525 b may identify the packets to be duplicated. The packets maybe received from one of the servers 106 via the network 104″, and may bestored and maintained on server-side appliance 200 b (e.g., on thedatabase 530 b) or on the dedicated appliance 200 c (e.g., on thedatabase 530 c). In some embodiments, the delivery handler 525 b mayaccess the database 530 b on the server-side appliance 200 b to identifyand retrieve the packets to be duplicated. In some embodiments, thedelivery handler 525 b may access the database 530 c on the dedicatedappliance 200 c to identify and retrieve the packets to be duplicated.The packets identified from the database 530 b or 530 c may be thepackets to be buffered, to undergo signature matching, or any otheradditional processing at the server-side appliance 200 b or thededicated appliance 200 c. In some embodiments, the delivery handler 525b may receive the packets duplicated by the packet processor 540 fromthe dedicated appliance 200 c. As described above, the packet processor540 may send duplicates of the packets to the server-side appliance 200c concurrent to performing processing on the original packets receivedfrom the server 106. In some embodiments, the delivery handler 525 b mayintercept, receive, or otherwise identify the packets sent from theserver 106 destined to one of the clients 102. In some embodiments, thedelivery handler 525 b may parse each packet to be duplicated toidentify a sequence number. The delivery handler 525 b may maintain thesequence numbers of the packets to be duplicated on the database 530 b.With the identification of each packet, the delivery handler 525 b maygenerate the duplicate of the packet to send to the client-sideappliance 200 a via the selected link 535 a-n.

Along with the duplicated packets, the delivery handler 525 b may alsosend information to hold the duplicates of the one or more packets atthe client-side appliance 200 a. The information may correspond to atleast one of the duplicated packets. The information may include acommand (sometimes referred herein as a flag) to hold the packet and anamount of time to hold the packet. For example, the information may bein the form “{Hold flag|Delay=30 ms}” to indicate to the client-sideappliance 200 a to hold the duplicated packet for 30 ms. In someembodiments, the information may an indicator signaling that the packetis a duplicated packet. In some embodiments, the delivery handler 525 bmay insert the information into each duplicated packet (e.g., in theheader or payload data). In some embodiments, the delivery handler 525 bmay send the information as a separate packet to send along with theduplicates of packets via the selected link 535 a-n. With the generationof the information, the delivery handler 525 b may transmit theduplicated packets to the client-side appliance 200 a along the selectedlink 535 a-n. In some embodiments, the delivery handler 525 b maytransmit the duplicated packets to the client-side appliance 200 a viathe selected link 535 a-n, instead of the original packets received fromthe server 106.

In some embodiments, the delivery handler 525 b may send one or morepackets identified subsequent to the processing of the packetscorresponding to the duplicated packets to the client-side appliance 200a. The processing of the packets may be at the server-side appliance 200b or the dedicated appliance 200 c. The one or more packets may includethe packets received at the server-side appliance 200 b or the dedicatedappliance 200 c subsequent to performance of one or more operations to aprior set of packets corresponding to the duplicated packets. Forexample, as explained above, the number of received packets may be lessthan the threshold number for carrying out signature comparison, as theelapsed time may reach the threshold time limit due to the congestionwindow size. Consequently, the packets may be received subsequent to thesignature comparison. In some embodiments, the delivery handler 525 bmay identify the one or more packets received subsequent to theprocessing by accessing the database 530 b of the server-side appliance200 b or the database 530 c of the dedicated appliance 200 c. Thedelivery handler 525 b may send or forward the one or more packetsreceived subsequent to the processing via the link 535 a-n identified ashaving the lowest latency. In some embodiments, the delivery handler 525b may send the one or more packets received subsequent to the processingwithout duplication of the packets.

From the server-side appliance 200 b, the delivery handler 525 aexecuting on the client-side appliance 200 a may receive the duplicatedone or more packets with the information. The delivery handler 525 a maystore or maintain the duplicated packets received from the server-sideappliance 200 b on the database 530 a. In some embodiments, the deliveryhandler 525 a may store the duplicated packets onto a buffer maintainedon the database 530 a. The delivery handler 525 a may parse theinformation received with the duplicated packets to identify the commandto hold and the amount of time to hold at the client-side appliance 200a. In some embodiments, upon receipt of the duplicated packet, thedelivery handler 525 a may maintain a timer to keep track of a timeelapsed since the receipt of the duplicated packet from the server-sideappliance 200 b. The delivery handler 525 a may compare the elapsed timeto the amount of time to hold as specified in the information sent withthe duplicated packet. When the elapsed time is less than the amount oftime, the delivery handler 525 a may continue to hold or maintain theduplicated packet on the database 530 a. On the other hand, when theelapsed time is greater than or equal to the amount of time, thedelivery handler 525 a may delete or no longer maintain the duplicatedpacket from the database 530 a.

In some embodiments, as more and more duplicated packets are receivedfrom the server-side appliance 200 b, the delivery handler 525 a maysend a feedback signal to the server-side appliance 200 b to ceasetransmission of the duplicated packets. The delivery handler 525 a maymaintain a counter to keep track of a number of the duplicated packetsmaintained on the database 530 a. Each time the counter is incremented,the delivery handler 525 a may compare the number of duplicated packetsto a threshold number. The threshold number may correspond to a maximumnumber of packets permitted to be maintained on the client-sideappliance 200 a by the size capacity of database 530 a. When the numberof duplicated packets is less than or equal to the threshold number, thedelivery handler 525 a may allow storage of the duplicated packet on thedatabase 535 a. In contrast, when the number of duplicated packets isgreater than the threshold number, the delivery handler 525 a may sendthe feedback signal to the server-side appliance 200 b via the network104′ to cease transmission of the duplicated packets. The feedbacksignal may include a termination command (or flag) to indicate to theserver-side appliance 200 b to stop transmission of the duplicatedpackets. Upon receipt of the feedback signal, the delivery handler 525 bon the server-side appliance 200 b may terminate transmission of theduplicated packets to the client-side appliance 200 a.

Concurrent with or subsequent to the transmission of the duplicatedpackets, the delivery handler 525 b may identify or receive anindication to drop or send the duplicates of the packets at theclient-side appliance 200 a. The indication may be any sign that theduplicates of the packets maintained on the database 530 a of theclient-side appliance 200 a is to be dropped or sent to the client 102.In some embodiments, the indication may be at least one control signal.The control signal may include a command (or flag) to drop theduplicated packets or a command (or flag) to send the duplicated packetsto the client 102. In some embodiments, the control signal may include aset of sequence numbers for packets to be dropped or sent. In someembodiments, the delivery handler 525 b may identify the sequencenumbers of the duplicated packets sent to the client-side appliance 200a over the selected link 535 a-n. The delivery handler 525 b may insertor include the sequence numbers of duplicated packets into the controlsignal. In some embodiments, a subset of the duplicated packets may beindicated as to be dropped, while another subset of the duplicatedpackets may be indicated as to be sent. Each subset may be indexed oridentified using the sequence numbers. With the receipt of theindication, the delivery handler 525 b may in turn transmit theindication to the client-side appliance 200 a over the network 104′. Theindication may be sent over the selected link 535 a-n or the link 535a-n with the lowest latency to the client-side appliance 200 a.

In some embodiments, the delivery handler 525 b may receive theindication (e.g., the control signal) from the packet processor 540executing on the server-side appliance 200 b or the dedicated appliance200 c. Upon completion of the performance of the operation on the one ormore packets corresponding to the duplicated, the packet processor 540may generate the indication based on the results of the operation. Asexplained above, the operation may include the buffering of the packets,signature matching on the packets, or, other processing, among others.For example, when the processing of the packets is successful (e.g.,successful signature matching), the packet processor 540 may generatethe indication to send the duplicated packets to the client 102. In someembodiments, the packet processor 540 may identify the sequence numberof the corresponding duplicated packets corresponding to packets inwhich the processing (e.g., security inspection) is successful. On theother hand, when the processing of the packets is not successful (e.g.,failure in signature matching), the packet processor 540 may generatethe indication to drop the duplicated packets maintained on the database530 a. In some embodiments, the packet processor 540 may identify thesequence number of the corresponding duplicated packets corresponding topackets in which the processing is not successful. As discussed above,the packet processor 540 may maintain the sequence number of previouslyduplicated packets. With the generation of the indication, the packetprocessor 540 may send or relay the indication to the delivery handler525 b. The delivery handler 525 b in turn may transmit the indication tothe client-side appliance 200 a via the network 104′.

From the server-side appliance 200 b via the network 104′, the deliveryhandler 525 a executing on the client-side appliance 200 a may receivethe indication. In accordance with the indication received from theserver-side appliance 200 b, the delivery handler 525 a may send or dropthe duplicated packets maintained on the database 530 a of theclient-side appliance 200 a. When the indication is to send theduplicate packets, the delivery handler 525 a may forward, send, ortransmit the duplicate packets to the client 102 via the network 104. Insome embodiments, the delivery handler 525 a may send the duplicatedpackets maintained on the database 530 a to the client 102, instead ofthe original packets from the server 106. Conversely, when theindication is to drop the duplicate packets, the delivery handler 525 amay drop, remove, or otherwise prevent transmission of the duplicatepackets to the client 102. In some embodiments, the delivery handler 525a may prevent transmission of the duplicated packets and the originalpackets to the client 102.

The delivery handler 525 a may determine or identify whether to drop orto send the duplicated packets on an individual basis. For eachduplicated packet maintained on the database 530 a, the delivery handler525 a may parse the indication to identify whether to send or drop thepacket. In some embodiments, the delivery handler 525 a may parse thesequence numbers from the indication to identify which duplicatedpackets to drop and which duplicated packets to send to the client 102.In some embodiments, the delivery handler 525 a may identify the commandfor the duplicated packet corresponding to the sequence number of theindication. If the indication is to send the duplicate packet, thedelivery handler 525 a may forward, send, or transmit the duplicatepacket to the client 102 via the network 104. In some embodiments, thedelivery handler 525 a may transmit the duplicate packet to the client102, instead of the original packet from the server 106. The deliveryhandler 525 a may compare the sequence number of each additionalreceived packet to the sequence number of the duplicated packetindicated as to be sent. The additional received packet may be receivedby the client-side appliance 200 a separately from duplicate packets. Ifthe sequence numbers match, the delivery handler 525 a may send theduplicate packet, instead of the original packet. Conversely, if theindication is to drop the duplicate packet, the delivery handler 525 amay drop or remove the duplicate packet from the database 350 a. In someembodiments, the delivery handler 525 a may prevent transmission of theduplicated packet to the client 102 via the network 104. The deliveryhandler 525 a may also prevent transmission of the original packet fromthe server 106 to the client 102. The delivery handler 525 a may comparethe sequence number of each additional received packet to the sequencenumber of the duplicated packet indicated as to be sent. The additionalreceived packet may be received by the client-side appliance 200 aseparately from duplicate packets. If the sequence numbers match, thedelivery handler 525 a may restrict or prevent forwarding of theadditional packet to the client 102.

Because the duplicated packets are already stored on client-sideappliance 200 a and may be dropped or sent to the client 102 when theprocessing (e.g., security inspection) is completed, the additionalprocessing of the packet may not incur additional delay in receipt ofthe packet. Furthermore, since a link 535 a-n besides the one with thelowest latency is selected to transmit the duplicated packets to theclient-side appliance 200 a, over-utilization of the link 535 a-n withthe lowest latency may be prevented. In this manner, latency, jitter,and packet loss over the network 104′ may be reduced and consequentlythe quality of service over the network 104′ may be improved.

In some embodiments, the functionalities and operations performed by theclient-side appliance 200 a and the server-side appliance 200 b may beswitched or transposed. For example, the dedicated appliance 200 c mayreside on the client-side, and in communication with the clients 102 andthe client-side appliance 200 a. The delay estimator 510 a of theclient-side appliance 200 a may perform the same functionalities as thedelay estimator 510 b of the server-side appliance 200 b as detailedabove in identifying the delay penalty incurred from processing of thepackets by the client-side appliance 200 a or the dedicated appliance200 c. The path quality estimator 510 a of the client-side appliance 200a may perform the same functionalities as the path quality estimator 510b of the server-side appliance 200 b in determining the latencies of thelinks 535 a-n. The link selector 520 a of the client-side appliance 200a may perform the same functionalities as the link selector 520 b of theserver-side appliance 200 b as detailed above in selecting the links 535a-n. The delivery handler 525 a of the client-side appliance 200 a mayperform the same functionalities as the delivery handler 525 b of theserver-side appliance 200 b as detailed above in managing packets.

Referring now to FIG. 6, depicted is a flow diagram for a method 600 ofpath selection proportional to a penalty delay in processing packets.The functionalities of method 600 may be implemented using, or performedby, the components described in FIGS. 1-5, such as the clients 102, theservers 106, or appliance 200 a-n. In brief overview, a server-sideappliance may identify a delay penalty (605). The server-side appliancemay select a link (610). The server-side appliance may transmitduplicates (615). A client-side appliance may receive the duplicates(620). The client-side appliance may hold the duplicates (625). Theserver-side appliance may send a control signal (630). The client-sideappliance may receive the control signal (635). The client-sideappliance may determine whether to drop or send (640). If drop, theclient-side appliance may drop the duplicates (645). On the other hand,if send, the client-side appliance may forward the duplicates (650).

In further detail, a server-side appliance (e.g., the server-sideappliance 200 b) may identify a delay penalty (605). The delay penaltymay correspond to an amount of time to be incurred in processing thepackets by the server-side appliance or a dedicated appliance (e.g., thededicated appliance 200 c). The processing of the packets may includeoperations, such as buffering, signature matching for securityinspection, or other types of heavy processing (e.g., encryption). Todetermine the delay penalty, the server-side appliance may identify anoperation to be performed on the packets. The server-side appliance mayidentify a threshold time as the delay penalty for buffering. Theserver-side appliance may identify a round-trip time between theserver-side appliance and the dedicated appliance as the delay penaltyfor signature matching.

The server-side appliance may select a link (e.g., the link 535 a-n)(610). The server-side appliance may also identify a latency for eachlink over a network (e.g., the network 104′) between a client-sideappliance (e.g., the client-side appliance 200 a) and the server-sideappliance. The latency may be due to network conditions over the link.The server-side appliance may identify the link with the lowest latency,and may exclude the link with the lowest latency from selection. Fromeach of the remaining links, the server-side appliance may determine adeviation from the lowest latency. The server-side appliance may thenidentify the link with the deviation greater than or equal to the delaypenalty.

The server-side appliance may transmit duplicates (615). The server-sideappliance may generate and send duplicates of packets over the selectedlink. The server-side appliance may identify the packets to beduplicated by accessing a database on the server-side appliance or thededicated appliance (e.g., the database 530 b or 530 b). The packets tobe duplicated may have originally been from a server (e.g., the server106). A client-side appliance (e.g., the client-side appliance 200 a)may receive the duplicates (620). The client-side appliance may receivethe duplicate of packets from the server-side appliance. The client-sideappliance may hold the duplicates (625). The client-side appliance maymaintain the duplicate packets on a database (e.g., the database 530 a).

The server-side appliance may send a control signal (630). Theserver-side appliance may receive the control signal from the dedicatedappliance, upon completion of the buffering, security inspection, orother processing on the original packets corresponding to the duplicatepackets. The control signal may include a command indicating that theclient-side appliance is to drop or send the duplicate packets based onthe results of the processing of the packets. The client-side appliancemay receive the control signal (635). The client-side appliance mayparse the control signal to identify the command. The client-sideappliance may determine whether to drop or send the packets to theclient (640). The client-side appliance may drop or send the duplicatepackets maintained on the database in accordance to the command of thecontrol signal. If the packets are to be dropped, the client-sideappliance may drop the duplicates (645). The client-side appliance mayrestrict transmission of the duplicate packets and the correspondingoriginal packets from the server to a client (e.g., the client 102). Onthe other hand, if the packets are to be sent, the client-side appliancemay forward the duplicates (650). The client-side appliance may send theduplicate packets maintained on the database to the client, instead ofthe original packets form the server.

Various elements, which are described herein in the context of one ormore embodiments, may be provided separately or in any suitablesubcombination. For example, the processes described herein may beimplemented in hardware, software, or a combination thereof. Further,the processes described herein are not limited to the specificembodiments described. For example, the processes described herein arenot limited to the specific processing order described herein and,rather, process blocks may be re-ordered, combined, removed, orperformed in parallel or in serial, as necessary, to achieve the resultsset forth herein.

It should be understood that the systems described above may providemultiple ones of any or each of those components and these componentsmay be provided on either a standalone machine or, in some embodiments,on multiple machines in a distributed system. The systems and methodsdescribed above may be implemented as a method, apparatus or article ofmanufacture using programming and/or engineering techniques to producesoftware, firmware, hardware, or any combination thereof. In addition,the systems and methods described above may be provided as one or morecomputer-readable programs embodied on or in one or more articles ofmanufacture. The term “article of manufacture” as used herein isintended to encompass code or logic accessible from and embedded in oneor more computer-readable devices, firmware, programmable logic, memorydevices (e.g., EEPROMs, ROMs, PROMs, RAMs, SRAMs, etc.), hardware (e.g.,integrated circuit chip, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), etc.), electronicdevices, a computer readable non-volatile storage unit (e.g., CD-ROM,USB Flash memory, hard disk drive, etc.). The article of manufacture maybe accessible from a file server providing access to thecomputer-readable programs via a network transmission line, wirelesstransmission media, signals propagating through space, radio waves,infrared signals, etc. The article of manufacture may be a flash memorycard or a magnetic tape. The article of manufacture includes hardwarelogic as well as software or programmable code embedded in a computerreadable medium that is executed by a processor. In general, thecomputer-readable programs may be implemented in any programminglanguage, such as LISP, PERL, C, C++, C#, PROLOG, or in any byte codelanguage such as JAVA. The software programs may be stored on or in oneor more articles of manufacture as object code.

While various embodiments of the methods and systems have beendescribed, these embodiments are illustrative and in no way limit thescope of the described methods or systems. Those having skill in therelevant art can effect changes to form and details of the describedmethods and systems without departing from the broadest scope of thedescribed methods and systems. Thus, the scope of the methods andsystems described herein should not be limited by any of theillustrative embodiments and should be defined in accordance with theaccompanying claims and their equivalents.

It will be further understood that various changes in the details,materials, and arrangements of the parts that have been described andillustrated herein may be made by those skilled in the art withoutdeparting from the scope of the following claims.

We claim:
 1. A method comprising: communicating, by a first device and asecond device, one or more packets over a link selected from a pluralityof links based at least on latency; receiving, by the first device, anindication to one of drop or send duplicates of one or more packets sentby the first device to the second device; and transmitting, by the firstdevice, the indication to the second device to cause the second deviceto one of drop or send the duplicates of the one or more packetsaccording to the indication.
 2. The method of claim 1, furthercomprising identifying, by the first device, a delay penalty forprocessing one or more packets communicated between the first device andthe second device.
 3. The method of claim 2, further comprisingselecting the link from the plurality of links based on a latency of thelink deviating from the latency of at least one other link of theplurality of links by at least the delay penalty.
 4. The method of claim1, further comprising determining the delay penalty based at least on anumber of round trip times to send a number of packets via the link. 5.The method of claim 1, further comprising transmitting, by the firstdevice to the second device, duplicates of the one or more packets viathe link with information indicating to the second device to hold theduplicates of the one or more packets at the second device.
 6. Themethod of claim 1, wherein the first device and second device areintermediary to a plurality of clients and a plurality of servers. 7.The method of claim 6, further comprising communicating between thefirst device and the second device packets between the plurality ofclients and the plurality of servers using the plurality of links, eachof the plurality of links having different latencies.
 8. A systemcomprising: a first device in a communication with a second via aplurality of links; wherein the first device is configured to:communicate one or more packets over a link selected from the pluralityof links based at least on latency; receive an indication to sendduplicates of one or more packets sent by the first device to the seconddevice; and transmit the indication to the second device to cause thesecond device to send the duplicates of the one or more packets.
 9. Thesystem of claim 8, wherein the first device is further configured todetermine a delay penalty for processing one or more packetscommunicated between the first device and the second device via thelink.
 10. The system of claim 9, wherein the first device is furtherconfigured to select the link from the plurality of links based on alatency of the link deviating from the latency of at least one otherlink of the plurality of links by at least the delay penalty.
 11. Thesystem of claim 8, wherein the first device is further configured todetermine the delay penalty based at least on a number of round triptimes to send a number of packets via the link.
 12. The system of claim8, wherein the first device is further configured to transmit to thesecond device duplicates of the one or more packets via the link withinformation indicating to the second device to hold the duplicates ofthe one or more packets at the second device.
 13. The system of claim 8,wherein the first device and second device are intermediary to aplurality of clients and a plurality of servers and are configured tocommunicate packets between the plurality of clients and the pluralityof servers using the plurality of links, each of the plurality of linkshaving different latencies.
 14. A system comprising: a first device in acommunication with a second via a plurality of links; wherein the firstdevice is configured to: communicate one or more packets over a linkselected from the plurality of links based at least on latency; receivean indication to one of drop the duplicates of one or more packets sentby the first device to the second device; and transmit the indication tothe second device to cause the second device to drop the duplicates ofthe one or more packets.
 15. The system of claim 14, wherein the firstdevice is further configured to determine a delay penalty for processingone or more packets communicated between the first device and the seconddevice via the link.
 16. The system of claim 15, wherein the firstdevice is further configured to select the link from the plurality oflinks based on a latency of the link deviating from the latency of atleast one other link of the plurality of links by at least the delaypenalty.
 17. The system of claim 15, wherein the first device is furtherconfigured to determine the delay penalty based at least on a number ofround trip times to send a number of packets via the link.
 18. Thesystem of claim 14, wherein the first device is further configured totransmit to the second device duplicates of the one or more packets viathe link with information indicating to the second device to hold theduplicates of the one or more packets at the second device.
 19. Thesystem of claim 14, wherein the first device and second device areintermediary to a plurality of clients and a plurality of servers. 20.The system of claim 14, wherein the first device and second device areconfigured to communicate packets between the plurality of clients andthe plurality of servers using the plurality of links, each of theplurality of links having different latencies.